A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

Oct 9 2026 -- Eyad Amr -- GitHub -- Discord

Ladies and gentlemen. Have you ever been kicked in the head by a donkey? Well most of us (hopefully) have not been literally kicked in the head by any animal, but if we talk about this figuratively, you've faced the many amounts of:

• "rustc [E0597]: borrowed value does not live long enough"
• "error[E0499]: cannot borrow v as mutable more than once at a time"
• "error[E0502]: cannot borrow v as immutable because it is also borrowed as mutable"

This is an OPML version of the HN Popularity Contest results for 2025, for importing into RSS feed readers.

Plug: if you want to find content related to your interests from thousands of obscure blogs and noisy sources like HN Newest, check out Scour. It's a free, personalized content feed I work on where you define your interests in your own words and it ranks content based on how closely related it is to those topics.

A skill file you drop into Claude Code, Cursor, or Codex. Ask for an object, get a clean isometric figure in the dark hairline "technical drawing" style, as SVG or canvas code. Ask for motion, get a seamless loop.

Everything in this gist was made with it. No hand-drawn lines.

Claude Code (personal, all projects):

This repo is full of low-signal unit tests. Modern agents write tests that restate the implementation, always pass, break on every refactor, and catch almost nothing our stronger tests already miss.

Delete every unit test that would not catch a real bug an end-to-end or integration test would miss. Prefer a smaller suite that protects behavior over a large suite that protects coverage numbers.

Keep a test only if all of these are true:

• It protects an observable behavior, invariant, or public contract.
• There is a credible regression that would make it fail.
• Existing E2E or integration coverage does not already catch that failure.
• It would survive a behavior-preserving refactor. If it breaks only because an internal name, call shape, or mock changed, delete it.